Techniques for monitoring virtualized network functions or network functions virtualization infrastructure

ABSTRACT

Examples may include techniques for monitoring virtual network functions or network functions virtualization infrastructure. Examples include receiving performance measurement data from virtualized network functions arranged to support a network service or from network functions virtualization infrastructure composed to support the virtualized network functions. In some examples, corrective actions such as virtualized network function lifecycle management operations are initiated based on the received performance measurement data.

RELATED CASE

This application is a continuation of U.S. patent application Ser. No.15/887,915 filed on Feb. 2, 2018 which is a continuation of U.S. patentapplication Ser. No. 14/751,499 filed on Jun. 26, 2015, which claimspriority to and the benefit of U.S. Provisional Patent Application No.62/134,941 filed on Mar. 18, 2015, and U.S. Provisional PatentApplication No. 62/102,991 filed on Jan. 13, 2015 both are herebyincorporated by reference in their entirety.

TECHNICAL FIELD

Examples described herein are generally related to wirelesscommunication networks.

BACKGROUND

Traditionally, equipment for wireless communications networks may bedeployed as physical equipment having software and hardware boundtogether. However, virtualization technologies have evolved to supportnetwork function software that may be executed by commercialoff-the-shelf (COTS) hardware. Use of virtualization technologies mayallow for a more flexible, quickly deployable or cost effective wirelesscommunication network to be built and maintained. But these virtualizednetworks may be based on disaggregated physical elements (e.g.,processors, memory, storage) composed to form virtualized resources(VRs) that support one or more types of virtualized network functions(VNFs). The VNFs may also be arranged to provide network services. Thesedisaggregated physical elements composed to form VRs may be widelydisbursed across various entities or locations that host the physicalequipment provisioned to compose the VRs. A management architecture andvarious management functions may be used to control and/or manage theone or more VNFs as well as the VRs allocated to support them. In somecases, the management architecture may be built on traditionalmanagement architectures and management functions that were used forcontrol or management of non-virtualized wireless communicationnetworks.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a first system.

FIG. 2 illustrates an example of a second system.

FIG. 3 illustrates an example process.

FIG. 4 illustrates an example block diagram for a first apparatus.

FIG. 5 illustrates an example of a first logic flow.

FIG. 6 illustrates an example of a first storage medium.

FIG. 7 illustrates an example block diagram for a second apparatus.

FIG. 8 illustrates an example of a second logic flow.

FIG. 9 illustrates an example of a second storage medium.

FIG. 10 illustrates an example of a device.

FIG. 11 illustrates an example of a broadband wireless access system.

DETAILED DESCRIPTION

Examples are generally directed to improvement for monitoringvirtualized network functions (VNFs) or network functions virtualizationinfrastructure (NFVI). Wireless mobile broadband technologies mayinclude any wireless technologies suitable for use with wireless devicesor user equipment (UE), such as one or more third generation (3G),fourth generation (4G) or emerging fifth generation (5G) wirelessstandards, revisions, progeny and variants. Examples of wireless mobilebroadband technologies may include without limitation any of theInstitute of Electrical and Electronics Engineers (IEEE) 802.16m and802.16p standards, 3rd Generation Partnership Project (3GPP) Long TermEvolution (LTE) and LTE-Advanced (LTE-A) standards, and InternationalMobile Telecommunications Advanced (IMT-ADV) standards, including theirrevisions, progeny and variants. Other suitable examples may include,without limitation, Global System for Mobile Communications(GSM)/Enhanced Data Rates for GSM Evolution (EDGE) technologies,Universal Mobile Telecommunications System (UMTS)/High Speed PacketAccess (HSPA) technologies, Worldwide Interoperability for MicrowaveAccess (WiMAX) or the WiMAX II technologies, Code Division MultipleAccess (CDMA) 2000 system technologies (e.g., CDMA2000 1×RTT, CDMA2000EV-DO, CDMA EV-DV, and so forth), High Performance Radio MetropolitanArea Network (HIPERMAN) technologies as defined by the EuropeanTelecommunications Standards Institute (ETSI) Broadband Radio AccessNetworks (BRAN), Wireless Broadband (WiBro) technologies, GSM withGeneral Packet Radio Service (GPRS) system (GSM/GPRS) technologies, HighSpeed Downlink Packet Access (HSDPA) technologies, High Speed OrthogonalFrequency-Division Multiplexing (OFDM) Packet Access (HSOPA)technologies, High-Speed Uplink Packet Access (HSUPA) systemtechnologies, 3GPP Rel. 8, 9, 10 or 11 of LTE/System ArchitectureEvolution (SAE), and so forth. The examples are not limited in thiscontext.

By way of example and not limitation, various examples may be describedwith specific reference to various 3GPP radio access network (RAN)standards, such as the 3GPP Universal Terrestrial Radio Access Network(UTRAN), the 3GPP Evolved Universal Terrestrial Radio Access Network(E-UTRAN) and 3GPP's suite of UMTS and LTE/LTE-Advanced TechnicalSpecifications (in case of LTE/LTE-Advanced collectively “3GPP LTESpecifications” according to the 36 Series of Technical Specifications),and IEEE 802.16 standards, such as the IEEE 802.16-2009 standard andcurrent third revision to IEEE 802.16 referred to as “802.16Rev3”consolidating standards 802.16-2009, 802.16h-2010 and 802.16m-2011, andthe IEEE 802.16p draft standards including IEEE P802.16.1b/D2 Jan. 2012titled “Draft Amendment to IEEE Standard for WirelessMAN-Advanced AirInterface for Broadband Wireless Access Systems, Enhancements to SupportMachine-to-Machine Applications” (collectively “IEEE 802.16 Standards”),and any drafts, revisions or variants of the 3GPP LTE Specifications andthe IEEE 802.16 Standards. Although some embodiments may be described asa 3GPP LTE Specifications or IEEE 802.16 Standards system by way ofexample and not limitation, it may be appreciated that other types ofcommunications system may be implemented as various other types ofmobile broadband communications systems and standards. The examples arenot limited in this context.

As contemplated in the present disclosure, a management architectureand/or various management functions may be used to control and/or manageone or more VNFs as well as the VRs allocated to support them. Also, ascontemplated in the present disclosure, some management architecturesmay be built on traditional management architectures and managementfunctions that were used to control or manage non-virtualized wirelesscommunication networks. However, due to the possibly diverse locationsof the physical elements provisioned or composed to execute or supportVRs, one entity in some virtualized environments may manage or controlan VNF and yet the physical elements (e.g., processors, storage, memory,etc.) composed to form VRs arranged to support the VNF may be managed orcontrolled by one or more other entities.

In some examples, for a virtualized environment where 3GPP operation andmanagement (OAM) entities are arranged to work with ETSI management andorchestration (MANO) entities for network functions virtualizations(NFV), a VNF may be supported by network function virtualizationsinfrastructure (NFVI) having various types of physical elements such asprocessors, storage or memory provisioned or composed to form VRs tosupport the VNF. For these examples, the VNF and NFVI may be operated orhosted by separate entities. As a result, traditional managementarchitectures and management functions may not work well since someimportant performance measurements (PMs) for NFVI supporting the VNF maynot be available for measuring by the entity hosting the NFV. Forexample, mean/peak processor usage for processors composed (e.g., vCPUs)to form at least part of a VR arranged to support the VNF. These PMs maybe important in order to deliver consistent and acceptable servicequality to end users of a 3GPP wireless network, as well as to timelyisolate and correct failure conditions. Also, the PMs may be needed toreflect ways in which the VNF may be impacted by the performance (orlack thereof) of VRs composed from physical elements in the NFVI tosupport the VNF. Therefore, PMs need to be measured and accessible forboth the VNF and for VRs composed from physical elements in the NFVI toeffectively and/or efficiently implement a management architectureand/or management functions in a virtualized wireless network. It iswith respect to these challenges that the examples described herein areneeded.

In some first examples, methods may be implemented that includereceiving first PM data for a VNF and receiving second PM data for NFVIarranged to support the VNF. These methods may also include determiningwhether to initiate a network services (NS) lifecycle management (LCM)operation with a network functions virtualization orchestrator (NFVO) ora VNF LCM operation with virtualized network function manager (VNFM)(e.g., both located with ETSI MANO entities) based on performing a PMdata correlation and detection of threshold crossing function using thefirst and/or the second PM data. As described more below either anelement manager (EM) or network manager (NM) of a 3GPP wireless networkmay include logic and/or features to receive the first and second PMdata and perform the detection of threshold crossing function todetermine whether to initiate the NS or VNF LCM operation.

In some second examples, methods may be implemented that includereceiving, at a virtualized infrastructure manager (VIM) for managingNFVI, PM data generated by the NFVI while the NFVI supports one or moreVNFs. These methods may also include forwarding the PM data to an NFVOif the PM data is related to a network service provided by the one ormore VNFs and forwarding the PM data to a VNFM arranged to manage theone or more VNFs if the PM data is related to one or more VRs composedfrom the NFVI and consumed while the VRs support the one or more VNFs.Both the VIM and NFVO may be located with ETSI MANO entities. Asdescribed more below, the NFVO and the VNFM may forward theirrespectively received PM data related to an EM or to an NM of a 3GPPwireless network for the EM or the NM to implement a PM data correlationand detection of threshold crossing function using the received PM datato determine whether to initiate an NS or VNF LCM operation.

FIG. 1 illustrates an example first system 100. In some examples, asshown in FIG. 1, system 100 includes 3GPP OAM 101 and ETSI MANO 103. Forthese examples, 3GPP OAM 101 and ETSI MANO 103 may include entities of avirtualized 3GPP specified core wireless network, for example, asdescribed in ETSI, group specification (GS), Network FunctionsVirtualisation (NFV); Management and Orchestration 001, V1.1.1,published in December of 2014, and/or previous or subsequent releases orversions (hereinafter referred to as ETSI GS NFV-MAN 001) or asdescribed in 3GPP technical review (TR) 32.842, entitled “TechnicalSpecification Group Services and System Aspects; Telecommunicationmanagement; Study on network management or virtualized networks”,Release 13, V1.0.0, published in March of 2015, and/or previous orsubsequent releases or versions (hereinafter referred to as 3GPP TR32.842). For example, as shown in FIG. 1, the 3GPP OAM 101 entities mayinclude a network manager (NM) 101, an element manager (EM) 120, avirtualized network function (VNF) 130 or a network functionsvirtualization infrastructure (NFVI) 140. Also, as shown in FIG. 1, ETSIMANO 103 entities may include a network functions virtualizationorchestrator (NFVO) 150, a virtualized network function manager (VNFM)160 and a virtualized infrastructure manager (VIM) 170.

According to some examples, NM 110 may be coupled with EM 120 viacommunication link (C.L.) 112 and with NFVO 150 via C.L. 144. EM 120 maybe coupled with VNF 130 via C.L. 122 and with VNFRM 160 via C.L. 124.VNF 130 may be coupled with NFVI 140 via C.L. 132 and with VNFM 160 viaC.L. 134. NFVI 140 may be coupled with VIM 170 via C.L. 144. Also, VIM170 may be coupled with NFVO 150 via C.L. 172. The above-mentionedcommunication links may be wireless, wired or a combination ofwireless/wired communication links to enable the various entities of3GPP OAM 101 and ETSI MANO 103 to communicatively couple with eachother.

In some examples, NM 110 may be arranged to manage various entitieswithin a 3GPP wireless network such as EM 120. NM 110 may provide apackage of functions with a responsibility for management of the 3GPPwireless network that may include network elements with virtualizednetwork functions (e.g., VNF 130) or non-virtualized network functions(e.g., EM 120) or both. The management provided by NM 110 may occurthrough one or more EMs such as EM 120 but may also involve directaccess to the network elements. Communications within the 3GPP wirelessnetwork may be based on open and well-standardized interfaces supportingmanagement of multi-vendor and multi-technology network elements such asthose possibly included in NFVI 140 or in other entities of 3GPP OAM 101or ETSI MANO 103.

In some examples, EM 120 may be arranged as a discretetelecommunications entity, which may be managed by NM 110 through aspecific interface, e.g. Itf-N. EM 120 may be arranged to manage one ormore VNFs such as VNF 130.

According to some examples, VNF 130 may represent one or more VNFsdeployed on or using NFVI 140. For these examples, NFVI 140 may includehardware (physical elements) and software components which may beprovisioned to compose virtualized resources (VRs) such as one or morevirtual machines in which the one or more VNFs of VNF 130 may besupported. In that regard, a given VNF may be supported by one or morevirtual machines and may be chained with other VNFs and/or physical,non-virtualized network functions to realize or provide a networkservice such as, but not limited to, e-mail services, virus scanningservices, web hosting services or data services. Components included inNFVI 140 may include possibly disaggregated physical elements that mayspan several locations such as processors, memory, storage, or networkswitching and may be hosted on multiple compute hosts or servers. Also,network resources that provide connectivity between these locations maybe regarded as part of NFVI 140. These disaggregated physical elementsmay be provisioned to execute a plurality of different types ofvirtualized resources composed or arranged to support the one or moreVNFs included in VNF 130 as these one or more VNFs provide a networkservice.

In some examples, NFVO 150 is an entity of ETSI MANO 103 that may bearranged to orchestrate VR or network services included in NFVIs such asNFVI 140 across multiple VIMs that may include VIM 170. NFVO 150 mayalso be arranged to implement network services (NS) LCM operation(s)155. NS LCM operation(s) 155 may include, but are not limited to,instantiate network service, terminate network service, query networkservice, scale network service, update network service, create VNFforwarding graph (VNFFG), delete VNFFG, query VNFFG, update VNFFG,create virtual link (VL), delete VL, update VL or query VL.

According to some examples, VNFM 160 is an entity of ETSI MANO 103 thatmay be arranged to manage one or more VNFs such as VNFs included in VNF130. VNFM 160 may also be arranged to implement VNF LCM operation(s)165. VNF LCM operation(s) 165 may include, but are not limited to,instantiate VNF instance, terminate VNF instance, query VNF instance,scale VNF instance or update VNF instance.

In some examples, VIM 170 is an entity of ETSI MANO 103 that may bearranged to control or manage NFVI 140. This control or management mayoccur within one or more operator infrastructure domains. VIM 170 may beable to receive PM data from PM data producers 145 that may include PMdata related to a network service provided by the one or more VNFsincluded in VNF 130. The PM data received from PM data producers 145 mayalso include PM data related to VRs included in NFVI 140 that may beconsumed while NFVI 140 supports the one or more VNFs included in VNF130. As described more below, logic and/or features of VIM 170 may becapable of splitting the received PM data based on whether the PM datais related to the network service or is related to the VRs.

According to some examples, as described more below, PM data from PMdata producer(s) 135 at VNF 130 and PM data producer(s) 145 at NFVI 140may be received by NM 110. NM 110 may receive the PM data from EM 120 orfrom entities at ETSI MANO 103 (e.g., routed through VIM 170, NFVO 150).For these examples, logic and/or features of NM 110 may implement orperform a PM data correlation and detection of threshold crossingfunction using the received PM data to determine whether to initiate NSLCM operation(s) 155 with NFVO 150.

In some examples, as described more below, PM data from PM dataproducer(s) 135 at VNF 130 and PM data producer(s) 145 may be eitherdirectly received by EM 120 from VNF 130 or may be routed throughentities at ETSI MANO 103 (e.g., routed through VIM 170 and VNFM 160)and then received by EM 120. For these examples, logic and/or featuresof EM 120 may implement or perform a PM data correlation and detectionof threshold crossing function using the received PM data to determinewhether to initiate VNF LCM operation(s) 165 with VNFM 160. In somealternative examples, EM 120 may recommend to NM 110 that VNF LCMoperation(s) 165 be initiated at VNFM 160. For these alternatives,responsive to this recommendation, EM 120 may cause NFVO 150 to initiateVNF LCM operation(s) 165 at VNFM 160.

According to some examples, as shown in FIG. 1, VNFM 160 may alsodirectly receive PM data generated by PM data producer(s) 165 from VNF130. For these examples, VNFM 160 may then forward the PM data to NFVO150. NFVO 150 may then use this PM data to orchestrate network servicesprovided by the one or more VNFs included in VNF 130. In some examples,NFVO 150 may initiate NS LCM operation(s) 155 based on the PM dataforwarded from VNFM 160.

FIG. 2 illustrates an example second system 200. In some examples, asshown in FIG. 2, system 200 includes a VNF 230 and an NFVI 240. Forthese examples, VNF 230 and NFVI 240 may be entities included in a 3GPPOAM such as 3GPP OAM 101 shown in FIG. 1 and these entities may becoupled with other entities within the 3GPP OAM or within an ETSI MANsuch as ETSI MAN 103. For example, as shown in FIG. 2, VNF 230 may becoupled with an EM via C.L. 222 and with a VNFM via C.L. 234. Also asshown in FIG. 2, NFVI 240 may be coupled with VNF 230 via C.L. 232 andwith a VIM via C.L. 244.

According to some examples, VNF 230 may include VNF application layerPMs 235 as shown in FIG. 2. For these examples, VNF application layerPMs 235 may reflect VNF application layer performance and may be sourcesof PM data produced or generated by one or more VNFs of VNF 230 whileproviding a network service to indicate the VNF application layerperformance. For example, VNF application layer PMs 235 may includecalls-per-second 235-1, number-of-subscribers 235-2, mean number ofdedicated EPS bearers 235-3 or maximum number of dedicated EPS bearers235-4. Examples are not limited to the various PM data sources includedin VNF application layer PMs 235, other and/or additional PM datasources are contemplated. As described more below, VNF 230 may report orsend PM data related to VNF application layer performance to an EMand/or to a VNFM.

In some examples, NFVI 240 may include VR PMs 245A as shown in FIG. 2.For these examples, VR PMs 245A may include various PMs related to VRsincluded in NFVI 240 consumed while supporting the one or more VNFs ofVNF 230. In other words, VR PMs 245A may be associated with the one ormore VNFs that consume VRs included in NFVI 240. For example,virtualized resource PMs 245A may include virtual central processingunit (vCPU) power usage 245A-1, virtual memory (VM) usageoversubscription 245A-2, VM disk latency 245A-3, mean vCPU usage 245A-4or maximum vCPU usage 245A-5. Examples are not limited to the various PMdata sources for VRs included in VR PMs 245A, other and/or additional PMdata sources are contemplated. As described more below, a VIM mayreceive PM data from NFVI 240 having VR PMs and may forward the PM datato a VNFM such as VNFM 160 in an ETSI MANO based on the PM dataincluding VR PMs. As described more below, VNFM 160 may forward the VRPM data to EM 120 managing the one or more VNFs for which consume theVRs associated with the VR PM data.

According to some examples, NFVI 240 may also include network servicePMs 245B as shown in FIG. 2. For these examples, network service PMs245B may include various PMs related to a network service provided bythe one or more VNFs of VNF 230. For example, network service PMs 245Bmay include virtual link usage 245B-1, average bandwidth used 245B-2,maximum bandwidth used 245B-3, number of VMs utilized 245B-4 or numberof vCPUs utilized 245B-5. Examples are not limited to the various PMdata sources included in network service PMs 245B, other and/oradditional PM data sources are contemplated. As described more below, aVIM may receive PM data from NFVI 240 having PMs related to a networkservice and may forward the PM data to another entity in an ETSI MANObased on the PM data including the PMs related to the network service.

FIG. 3 illustrates an example process 300. Process 300 may be formonitoring VNF or NFVI based on received PM data and determining whetherto initiate a VNF LCM operation based on the received PM and based onperforming a PM data correlation and detection of threshold crossingfunction. For these examples, elements of system 100 as shown in FIG. 1such as NM 110, EM 120, VNF 130, NFVI 140, NFVO 150, VNFM 160 or VIM 170may be related to process 300. Also types of PM data as described forand shown in FIG. 2 for system 200 may also be related to process 300.However, the example process 300 is not limited to implementations usingelements of system 100 or the types of PM data for system 200 shown inFIGS. 1-2.

Beginning at process 3.1 (Report PM Data), logic and/or features of VNF130 may be arranged to report PM data to EM 120 for a VNF arranged toprovide a network service. In some examples, the reported PM data may berelated to VNF application layer performance while providing the networkservice such as PMs included in VNF application layer PMs 235.

Moving to process 3.2 (Forward NFVI PM Data), logic and/or features ofVIM 170 may be arranged to forward received NFVI PM data to VNFM 160. Insome examples, the NFVI PM data may include PM data related to one ormore VRs composed from NFVI (from processors, memory, storage, etc.) andconsumed while supporting the VNF. For these examples, NFVI PM data mayinclude PM data such as that shown in FIG. 2 for VR PMs 245A.

Moving to process 3.3 (Forward NFVI PM Data), logic and/or features atVNFM 160 may forward NFVI PM data to EM 120 that may be arranged tomanage the VNF with which the VR PM data is associated.

Moving to process 3.4 (Perform PM Data Correlation and Detection ofThreshold Crossing Function), logic and/or feature at EM 120 may performor implement a PM data correlation and detection of threshold crossingfunction using the PM data received from VNF 130 and/or the NFVI PM dataforwarded from VNFM 160. For these examples, the PM data correlation anddetection of threshold crossing function may characterize networkperformance by correlating large numbers of received PMs. A thresholdmay be set for one, multiple or combinations of multiple types of PMs tomonitor certain performance measurements. The threshold, for example,may be tied to one or more quality of service (QoS) or service levelagreement (SLA) requirements that may dictate a desirable level ofperformance that should be maintained. A detection of a thresholdcrossing on a PM, groups of PMs or multiple types of PMs may be anindication of performance degradation or of recovery of some faultcondition and may trigger actions to mitigate network performance. Forexample, VM disk latency indicated in PMs for VRs composed from NFVI 140may exceeds a threshold that triggers actions or calls-per-secondhandled by the VNF fall below a threshold that triggers actions. A typeof action triggered to mitigate network performance may be a VNF LCMoperation as described in ETSI GS NFV-MAN 001 or TR 32.842.

Moving to process 3.5 (Initiate VNF LCM Operation), logic and/orfeatures of EM 120 may have determined that a VNF LCM operation wasneeded based on implementation of the PM data correlation and detectionof threshold crossing function using the PM data received from VNF 130and/or the NFVI PM data forwarded through VNFM 160.

Moving to process 3.6 (Perform VNF LCM Operation), logic and/or featuresof VNFM 160, VIM 170 and NFVO may be arranged to perform at leastportions of the VNF LCM operation initiated by EM 120. In some examples,the VNF LCM operation may include, but is not limited to, instantiateVNF instance, terminate VNF instance, query VNF instance, scale VNFinstance or update VNF instance.

Moving to process 3.7 (Forward NW Service NFVI PM Data), logic and/orfeatures of VIM 170 may forward network service NFVI PM data to NFVO150. In some examples, PM data related to the network service may be PMdata such as that included in network service PMs 245B that are relatedto the network service provided by the VNF of VNF 130.

Moving to process 3.8 (Forward NW Service NFVI PM Data), logic and/orfeatures of NFVO 150 may forward the network service NFVI PM data to NM110.

Moving to process 3.9 (Forward NW Service NFVI PM Data), logic and/orfeatures of VIM 170 may also forward the network service NFVI PM data toVNFM 160.

Moving to process 3.10 (Forward NW Service NFVI PM Data), logic and/orfeatures of VNFM 160 may forward the network service NFVI PM data to EM120.

Moving to process 3.11 (Forward PM Data), logic and/or features of EM120 may forward PM data to NM 110. In some examples, the PM data mayinclude VNF application layer performance PMs as mentioned above forprocess 3.1. The PM data may also include PM data related to one or moreVRs composed from NFVI and consumed while supporting the VNF asmentioned above for process 3.2.

Moving to process 3.12 (Perform PM Data Correlation and Detection ofThreshold Crossing Function), logic and/or features of NM 110 mayperform or implement a PM data correlation and detection of thresholdcrossing function using the PM data forwarded from EM 120 and/or theNFVI PM data forwarded from VNFO 150. For these examples, the PM datacorrelation and detection of threshold crossing function may be similarto the function performed by EM 120 in process 3.4. Also, actions may betriggered based on results of the PM data correlation and detection ofthreshold crossing function mentioned above for process 3.4. Forexamples a type of action triggered to mitigate network performance maybe an NS LCM operation as described in ETSI GS NFV-MAN 001 or TR 32.842.

Moving to process 3.13 (Initiate NS LCM Operation), logic and/orfeatures of NM 110 may have determined that an NS LCM operation wasneeded based on implementation of the PM data correlation and detectionof threshold crossing function using the PM data forwarded from EM 120and/or the network service NFVI PM data forwarded through NFVO 150.

Moving to process 3.14 (Perform NS LCM operation), logic and/or featuresof VNFM 160, VIM 170 and NFVO may be arranged to perform at leastportions of the NS LCM operation initiated by NM 110. In some examples,the NS LCM operation may include, but is not limited to, instantiatenetwork service, terminate network service, query network service, scalenetwork service, update network service, create VNFFG, delete VNFFG,query VNFFG, update VNFFG, create VL, delete VL, update VL or query VL.Process 300 may then come to an end.

FIG. 4 illustrates a block diagram for an example first apparatus. Asshown in FIG. 4, the example first apparatus includes apparatus 400.Although apparatus 400 shown in FIG. 4 has a limited number of elementsin a certain topology, it may be appreciated that the apparatus 400 mayinclude more or less elements in alternate topologies as desired for agiven implementation.

The apparatus 400 may comprise an apparatus 400 having a circuitry 420that may represent a portion of logic in hardware that may be generallyarranged to execute one or more other portions of logic that may includemodules 422-a. It is worthy to note that “a” and “b” and “c” and similardesignators as used herein are intended to be variables representing anypositive integer. Thus, for example, if an implementation sets a valuefor a=5, then a complete set of modules 422-a included in the one ormore other portions of logic may include modules 422-1, 422-2, 422-3,422-4 or 422-5. The examples are not limited in this context.

According to some examples, apparatus 400 may be implemented in networkequipment for an NM or EM for a 3GPP wireless network (e.g., NM 110 orEM 120). The EM or NM may be a functional entity for 3GPP OAM operatedas described in ETSI GS NFV-MAN 001 or 3GPP TR 32.842. The examples arenot limited in this context.

In some examples, as shown in FIG. 4, apparatus 400 includes circuitry420. Circuitry 420 can be any of various commercially availableprocessors, including without limitation an AMD® Athlon®, Duron® andOpteron® processors; ARM® application, embedded and secure processors;Qualcomm® Snapdragon, IBM®, Motorola® DragonBall®, Nvidia®Tegra® andPowerPC® processors; IBM and Sony® Cell processors; Intel® Celeron®,Core (2) Duo®, Core i3, Core i5, Core i7, Itanium®, Pentium®, Xeon®,Atom®, and XScale® processors; and similar processor. Dualmicroprocessors, multi-core processors, and other multi-processorarchitectures may also be employed as circuitry 420. According to someexamples, circuitry 420 may also be an application specific integratedcircuit (ASIC) and at least some modules 422-a may be implemented ashardware elements of the ASIC.

According to some examples, the logic of apparatus 400 may include a VNFPM data module 422-1. VNF PM data module 422-1 may be executed bycircuitry 420 to receive VNF PM data for a VNF. For these examples, theVNF PM data may be for a VNF arranged to provide a network service forthe 3GPP wireless network. The VNF PM data, if directed to an EM, may bereceived directly from a VNF entity of a 3GPP OAM. The VNF PM data, ifdirected to an NM, may be forwarded through an EM that is coupled withthe VNF entity. The VNF PM data may be included in VNF PM data 405 andmay be related to VNF application layer performance to include, but notlimited to, calls-per-second, number-of-subscribers, mean number ofdedicated EPS bearers in active mode or maximum or peak number ofdedicated EPS bearers in active mode.

In some examples, the logic of apparatus 400 may also include an NFVI PMdata module 422-2. NFVI PM data module 422-2 may be executed bycircuitry 420 to receive PM data for NFVI arranged to support the VNF.For these examples, the NFVI PM data may be included in NFVI PM data 410and may include PM data related to one or more VRs composed from theNFVI and consumed while supporting the VNF. This VR related PM data mayinclude vCPU power consumption, VM memory usage oversubscription, VMdisk latency, mean vCPU usage or maximum or peak vCPU usage. The NFVI PMdata may also be related to network services provided by the VNF. Thenetwork services related PM data may include latency of one or more VLssupporting the one or more VNFs, usage of the one or more VLs supportingthe one or more VNFs, average bandwidth used by the VNF to provide thenetwork service over a time interval, peak bandwidth used by the VNF toprovide the network service over the time interval, number of VMsutilized or composed for the VNF to provide the network service or vCPUsutilized or composed for the VNF to provide the network service.

According to some examples, the logic of apparatus 400 may also includea function module 422-3. Function module 422-3 may be executed bycircuitry 420 to implement or perform a PM data correlation anddetection of threshold crossing function to determine whether toinitiate a VNF or NS LCM operation with an NFVO or a VNFM. For theseexamples, the PM data correlation and detection of threshold crossingfunction may be implemented using the PM data included in VNF PM data405 and/or NFVI PM data 410.

In some examples, the logic of apparatus 400 may also include aninitiate module 422-4. Initiate module 422-4 may be executed bycircuitry 420 to initiate the VNF or NS LCM operation with the NFVO orthe VNFM. For these examples, initiate module may have determined that aVNF or NS LCM operation was needed based on implementation of the PMdata correlation and detection of threshold crossing function byfunction module 422-3 using the PM data included in VNF PM data 405and/or NFVI PM data 410. For example, average bandwidth used by the VNFto provide the network service over a time interval as indicated in NFVIPM data 410 may be below an average bandwidth threshold and correctiveactions may be needed that may include an NS LCM operation initiated bysending LCM operation 430 to the NFVO or may include a VNF LCM operationinitiated by sending LCM operation 430 to the VNFM.

According to some examples, the logic of apparatus 400 may also includeforward module 422-5. Forward module 422-5 may be executed by circuitry420 to forward VNF/NFVI PM data to an NM for the 3GPP wireless network.For these examples, apparatus 400 may be included in an EM for the 3GPPwireless network and the VNF/NFVI PM data received in VNF PM data 405and NFVI PM data 410 may be forwarded to the NM via VNF/NFVI PM data440. Also for these examples, the NM may also perform or implement thePM data correlation and detection of threshold crossing function usingthe VNF/NFVI PM data to determine whether a VNF LCM operation needs tobe initiated with NFVO.

Various modules of apparatus 400 and a device implementing apparatus 400may be communicatively coupled to each other by various types ofcommunications media to coordinate operations. The coordination mayinvolve the uni-directional or bi-directional exchange of information.For instance, the modules may communicate information in the form ofsignals communicated over the communications media. The information canbe implemented as signals allocated to various signal lines. In suchallocations, each message is a signal. Further embodiments, however, mayalternatively employ data messages. Such data messages may be sentacross various connections. Example connections include parallelinterfaces, serial interfaces, and bus interfaces.

Included herein is a set of logic flows representative of examplemethodologies for performing novel aspects of the disclosedarchitecture. While, for purposes of simplicity of explanation, the oneor more methodologies shown herein are shown and described as a seriesof acts, those skilled in the art will understand and appreciate thatthe methodologies are not limited by the order of acts. Some acts may,in accordance therewith, occur in a different order and/or concurrentlywith other acts from that shown and described herein. For example, thoseskilled in the art will understand and appreciate that a methodologycould alternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, not all acts illustratedin a methodology may be required for a novel implementation.

A logic flow may be implemented in software, firmware, and/or hardware.In software and firmware embodiments, a logic flow may be implemented bycomputer executable instructions stored on at least one non-transitorycomputer readable medium or machine readable medium, such as an optical,magnetic or semiconductor storage. The embodiments are not limited inthis context.

FIG. 5 illustrates an example of a first logic flow. As shown in FIG. 5,the first logic flow includes logic flow 500. Logic flow 500 may berepresentative of some or all of the operations executed by one or morelogic, features, or devices described herein, such as apparatus 500.More particularly, logic flow 500 may be implemented by VNF PM module422-1, NFVI PM data module 422-2, function module 422-3 or initiatemodule 422-4.

In the illustrated example shown in FIG. 5, logic flow 500 at block 502may receive first PM data for a VNF. In some examples, VNF PM datamodule 422-1 may receive the first PM data.

According to some examples, logic flow 500 at block 504 may receivesecond PM data for NFVI arranged to support the VNF. For these examples,NFVI PM data module 422-2 may receive the second PM data.

In some examples, logic flow 500 at block 506 may determine whether torequest an NS or VNF LCM operation with an NFVO or a VNFM based onperformance of a PM data correlation and detection of threshold crossingfunction using the first and/or the second PM data. For these examples,initiate module 422-4 may determine whether to initiate the NS or VNFLCM operation based on function module 422-3 performing the PM datacorrelation and detection of threshold crossing function using the firstand/or second PM data.

FIG. 6 illustrates an embodiment of a first storage medium. As shown inFIG. 6, the first storage medium includes storage medium 600. Storagemedium 600 may comprise an article of manufacture. In some examples,storage medium 600 may include any non-transitory computer readablemedium or machine readable medium, such as an optical, magnetic orsemiconductor storage. Storage medium 600 may store various types ofcomputer executable instructions, such as instructions to implementlogic flow 500. Examples of a computer readable or machine readablestorage medium may include any tangible media capable of storingelectronic data, including volatile memory or non-volatile memory,removable or non-removable memory, erasable or non-erasable memory,writeable or re-writeable memory, and so forth. Examples of computerexecutable instructions may include any suitable type of code, such assource code, compiled code, interpreted code, executable code, staticcode, dynamic code, object-oriented code, visual code, and the like. Theexamples are not limited in this context.

FIG. 7 illustrates a block diagram for an example second apparatus. Asshown in FIG. 7, the example second apparatus includes apparatus 700.Although apparatus 700 shown in FIG. 7 has a limited number of elementsin a certain topology, it may be appreciated that the apparatus 700 mayinclude more or less elements in alternate topologies as desired for agiven implementation.

The apparatus 700 may comprise an apparatus 700 having a circuitry 720that may represent a portion of logic in hardware that may be generallyarranged to execute one or more other portions of logic that may includemodules 722-a. It is worthy to note that “a” and “b” and “c” and similardesignators as used herein are intended to be variables representing anypositive integer. Thus, for example, if an implementation sets a valuefor a=4, then a complete set of modules 722-a included in the one ormore portions of logic may include modules 722-1, 722-2, 722-3 or 722-4.The examples are not limited in this context.

According to some examples, apparatus 700 may be implemented with orlocated at network equipment for a VIM arranged to manage NFVIsupporting one or more VNFs (e.g., VIM 170). The VIM may be a functionalentity for an ETSI MANO operated as described in ETSI GS NFV-MAN 001 or3GPP TR 32.842. The examples are not limited in this context.

In some examples, as shown in FIG. 7, apparatus 700 includes circuitry720. Circuitry 720 can be any of various commercially availableprocessors to include but not limited to the processors mentioned abovefor apparatus 400. Also, according to some examples, circuitry 720 mayalso be an ASIC and at least some modules 722-a may be implemented ashardware elements of the ASIC.

According to some examples, the logic of apparatus 700 may include aNFVI receive module 722-1. NFVI receive module 722-1 may be executed bycircuitry 720 to receive PM data generated by NFVI while the NFVIsupports one or more VNFs. For these examples, the PM data may beincluded in NFVI PM data 710.

In some examples, the logic of apparatus 700 may also include a network(NW) service(s) PM data module 722-2. NW service(s) PM data module 722-2may be executed by circuitry 720 to forward PM data to an NFVO if the PMdata is related to a network service provided by the one or more VNFs.For these examples, NW service PM data 730 may include the PM datarelated to the network service provided by the one or more VNFs.

According to some examples, the logic of apparatus 700 may also includea VR PM data module 722-3. VR PM data module 722-3 may be executed bycircuitry 720 to forward the PM data to a VNFM arranged to manage theone or more VNFs if the PM date is related to one or more VRs composedfrom the NFVI and consumed while the VR supports the one or more VNFs.For these examples, VR PM data 740 may include the PM data related tothe one or more VRs.

In some examples, the logic of apparatus 700 may also include an LCMmodule 722-4. LCM module 722-4 may be executed by circuitry 720 toperform an NS or VNF LCM operation that may have been initiated by an EMor an NM for a 3GPP wireless network for which the one or more VNFs areproviding the network service. For these examples, the NS or VNF LCMoperation may have been initiated responsive to the EM or NMimplementing a PM data correlation and detection of threshold crossingfunction using the PM data included in NW service PM data 730 or VR PMdata 740. In some examples, LCM indication 740 may have been forwardedfrom a VNFM for the VIM to perform an NS LCM operation which may includeinstantiate network service, terminate network service, query networkservice, scale network service, update network service, create VNFFG,delete VNFFG, query VNFFG, update VNFFG, create VL, delete VL, update VLor query VL. In some other examples, LCM indication 740 may have beenforwarded from the VNFM for the VIM to perform a VNF LCM operation whichmay include instantiate network service, terminate VNF instance, queryVNF instance, scale VNF instance or update VNF instance

Various modules of apparatus 700 and a device implementing apparatus 800may be communicatively coupled to each other by various types ofcommunications media to coordinate operations. The coordination mayinvolve the uni-directional or bi-directional exchange of information.For instance, the modules may communicate information in the form ofsignals communicated over the communications media. The information canbe implemented as signals allocated to various signal lines. In suchallocations, each message is a signal. Further embodiments, however, mayalternatively employ data messages. Such data messages may be sentacross various connections. Example connections include parallelinterfaces, serial interfaces, and bus interfaces.

FIG. 8 illustrates an example of a second logic flow. As shown in FIG.8, the second logic flow include logic flow 800. Logic flow 800 may berepresentative of some or all of the operations executed by one or morelogic, features, or devices described herein, such as apparatus 700.More particularly, logic flow 800 may be implemented by NFVI receivemodule 722-1, NW service(s) PM data module 722-2 or VR PM module 722-3.

In the illustrated example shown in FIG. 8, logic flow 800 at block 802may receive PM data generated by an NFVI while the NFVI supports one ormore VNFs. In some examples, the PM data may be received by NFVI receivemodule 722-1.

According to some examples, logic flow 800 at block 804 may forward thePM data to an NFVO if the PM data is related to a network serviceprovided by the one or more VNFs. For these examples, NW service(s) PMdata module 722-2 may forward the PM data.

In some examples, logic flow 800 at block 806 may forward the PM data toa VNFM arranged to manage the one or more VNFs if the PM data is relatedto one or more VRs composed from the NFVI and consumed while the VRsupports the one or more VNF S. For these examples, VR PM data module722-3 may forward the PM data.

FIG. 9 illustrates an embodiment of a second storage medium. As shown inFIG. 9, the second storage medium includes storage medium 900. Storagemedium 900 may comprise an article of manufacture. In some examples,storage medium 900 may include any non-transitory computer readablemedium or machine readable medium, such as an optical, magnetic orsemiconductor storage. Storage medium 900 may store various types ofcomputer executable instructions, such as instructions to implementlogic flow 800. Examples of a computer readable or machine readablestorage medium may include any tangible media capable of storingelectronic data, including volatile memory or non-volatile memory,removable or non-removable memory, erasable or non-erasable memory,writeable or re-writeable memory, and so forth. Examples of computerexecutable instructions may include any suitable type of code, such assource code, compiled code, interpreted code, executable code, staticcode, dynamic code, object-oriented code, visual code, and the like. Theexamples are not limited in this context.

FIG. 10 illustrates an embodiment of a device 1000 for use in abroadband wireless access network. Device 1000 may implement, forexample, apparatus 400/700, storage medium 600/900 and/or a logiccircuit 1070. The logic circuit 1070 may include physical circuits toperform operations described for apparatus 400/700. As shown in FIG. 10,device 1000 may include a radio interface 1010, baseband circuitry 1020,and computing platform 1030, although examples are not limited to thisconfiguration.

The device 1000 may implement some or all of the structure and/oroperations for the apparatus 400/700, storage medium 600/900 and/orlogic circuit 1070 in a single computing entity, such as entirely withina single device. Alternatively, the device 1000 may distribute portionsof the structure and/or operations for apparatus 400/700, storage medium600/900 and/or logic circuit 1070 across multiple computing entitiesusing a distributed system architecture, such as a client-serverarchitecture, a 3-tier architecture, an N-tier architecture, atightly-coupled or clustered architecture, a peer-to-peer architecture,a master-slave architecture, a shared database architecture, and othertypes of distributed systems. The examples are not limited in thiscontext.

In one embodiment, radio interface 1010 may include a component orcombination of components adapted for transmitting and/or receivingsingle carrier or multi-carrier modulated signals (e.g., includingcomplementary code keying (CCK) and/or orthogonal frequency divisionmultiplexing (OFDM) symbols and/or single carrier frequency divisionmultiplexing (SC-FDM) symbols) although the embodiments are not limitedto any specific over-the-air interface or modulation scheme. Radiointerface 1010 may include, for example, a receiver 1012, a transmitter1016 and/or a frequency synthesizer 1014. Radio interface 1010 mayinclude bias controls, a crystal oscillator and/or one or more antennas1018-f. In another embodiment, radio interface 1010 may use externalvoltage-controlled oscillators (VCOs), surface acoustic wave filters,intermediate frequency (IF) filters and/or RF filters, as desired. Dueto the variety of potential RF interface designs an expansivedescription thereof is omitted.

Baseband circuitry 1020 may communicate with radio interface 1010 toprocess receive and/or transmit signals and may include, for example, ananalog-to-digital converter 1022 for down converting received signals, adigital-to-analog converter 1024 for up converting signals fortransmission. Further, baseband circuitry 1020 may include a baseband orphysical layer (PHY) processing circuit 1026 for PHY link layerprocessing of respective receive/transmit signals. Baseband circuitry1020 may include, for example, a processing circuit 1028 for mediumaccess control (MAC)/data link layer processing. Baseband circuitry 1020may include a memory controller 1032 for communicating with MACprocessing circuit 1028 and/or a computing platform 1030, for example,via one or more interfaces 1034.

In some embodiments, PHY processing circuit 1026 may include a frameconstruction and/or detection module, in combination with additionalcircuitry such as a buffer memory, to construct and/or deconstructcommunication frames (e.g., containing subframes). Alternatively or inaddition, MAC processing circuit 1028 may share processing for certainof these functions or perform these processes independent of PHYprocessing circuit 1026. In some embodiments, MAC and PHY processing maybe integrated into a single circuit.

Computing platform 1030 may provide computing functionality for device1000. As shown, computing platform 1030 may include a processingcomponent 1040. In addition to, or alternatively of, baseband circuitry1020 of device 1000 may execute processing operations or logic forapparatus 400/700, storage medium 600/900, and logic circuit 1070 usingthe processing component 1040. Processing component 1040 (and/or PHY1026 and/or MAC 1028) may comprise various hardware elements, softwareelements, or a combination of both. Examples of hardware elements mayinclude devices, logic devices, components, processors, microprocessors,circuitry (e.g., circuitry 420 or 720), processor circuits, circuitelements (e.g., transistors, resistors, capacitors, inductors, and soforth), integrated circuits, application specific integrated circuits(ASIC), programmable logic devices (PLD), digital signal processors(DSP), field programmable gate array (FPGA), memory units, logic gates,registers, semiconductor device, chips, microchips, chip sets, and soforth. Examples of software elements may include software components,programs, applications, computer programs, application programs, systemprograms, software development programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an example isimplemented using hardware elements and/or software elements may vary inaccordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints, as desired for a given example.

Computing platform 1030 may further include other platform components1050. Other platform components 1050 include common computing elements,such as one or more processors, multi-core processors, co-processors,memory units, chipsets, controllers, peripherals, interfaces,oscillators, timing devices, video cards, audio cards, multimediainput/output (I/O) components (e.g., digital displays), power supplies,and so forth. Examples of memory units may include without limitationvarious types of computer readable and machine readable storage media inthe form of one or more higher speed memory units, such as read-onlymemory (ROM), random-access memory (RAM), dynamic RAM (DRAM),Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM(SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information.

Computing platform 1030 may further include a network interface 1060. Insome examples, network interface 1060 may include logic and/or featuresto support wireless network interfaces as described in one or more 3GPPLTE or LTE-A specifications or standards. For these examples, networkinterface 1060 may enable an apparatus 400 or 700 located at networkequipment such as an EM, NM or VIM.

Device 1000 may be, for example, a computer, a personal computer (PC), adesktop computer, a laptop computer, an ultrabook computer, asmartphone, a tablet computer, a notebook computer, a netbook computer,a work station, a mini-computer, multiprocessor system, processor-basedsystem, wireless access point, or combination thereof. Accordingly,functions and/or specific configurations of device 1000 describedherein, may be included or omitted in various embodiments of device1000, as suitably desired. In some embodiments, device 1000 may beconfigured to be compatible with protocols and frequencies associatedone or more of the 3GPP LTE Specifications and/or IEEE 802.16 Standardsfor WMANs, and/or other broadband wireless networks, cited herein,although the examples are not limited in this respect.

Embodiments of device 1000 may be implemented using single input singleoutput (SISO) architectures. However, certain implementations mayinclude multiple antennas (e.g., antennas 1018-j) for transmissionand/or reception using adaptive antenna techniques for beamforming orspatial division multiple access (SDMA) and/or using multiple inputmultiple output (MIMO) communication techniques.

The components and features of device 1000 may be implemented using anycombination of discrete circuitry, application specific integratedcircuits (ASICs), logic gates and/or single chip architectures. Further,the features of device 1000 may be implemented using microcontrollers,programmable logic arrays and/or microprocessors or any combination ofthe foregoing where suitably appropriate. It is noted that hardware,firmware and/or software elements may be collectively or individuallyreferred to herein as “logic” or “circuit.”

It should be appreciated that the exemplary device 1000 shown in theblock diagram of FIG. 10 may represent one functionally descriptiveexample of many potential implementations. Accordingly, division,omission or inclusion of block functions depicted in the accompanyingfigures does not infer that the hardware components, circuits, softwareand/or elements for implementing these functions would be necessarily bedivided, omitted, or included in examples.

FIG. 11 illustrates an embodiment of a broadband wireless access system1100. As shown in FIG. 11, broadband wireless access system 1100 may bean internet protocol (IP) type network comprising an internet 1110 typenetwork or the like that is capable of supporting mobile wireless accessand/or fixed wireless access to internet 1110. In one or moreembodiments, broadband wireless access system 1100 may comprise any typeof orthogonal frequency division multiple access (OFDMA) and/or multiplesingle carrier frequency division multiple access (multiple SC-FDMA)based wireless network, such as a system compliant with one or more ofthe 3GPP LTE Specifications and/or IEEE 802.16 Standards, and the scopeof this disclosure is not limited in these respects.

In the exemplary broadband wireless access system 1100, access servicenetworks (ASN) 1114, 1118 are capable of coupling with base stations(BS) 1114, 1120 (RRHs or eNBs), respectively, to provide wirelesscommunication between one or more fixed devices 1116 and internet 1110,or one or more mobile devices 1115 and Internet 1110. ASN 1112 mayimplement profiles that are capable of defining the mapping of networkfunctions to one or more physical entities on broadband wireless accesssystem 1100. Base stations 1114, 1120 (or eNBs) may comprise radioequipment to provide RF communication with fixed device 1116 and mobiledevice 1122, such as described with reference to device 1000 of FIG. 10,and may comprise, for example, the PHY, MAC, RLC or PDCP layer equipmentin compliance with a 3GPP LTE Specification or an IEEE 802.16 Standard.Base stations 1114, 1120 (or eNBs) may further comprise an IP backplaneto couple to Internet 1110 via ASN 1112, 1118, respectively, althoughthe scope of the claimed subject matter is not limited in theserespects.

Broadband wireless access system 1100 may further comprise a visitedconnectivity service network (CSN) 1124 capable of providing one or morenetwork functions including but not limited to proxy and/or relay typefunctions, for example authentication, authorization and accounting(AAA) functions, dynamic host configuration protocol (DHCP) functions,or domain name service controls or the like, domain gateways such aspublic switched telephone network (PSTN) gateways or voice over internetprotocol (VoIP) gateways, and/or internet protocol (IP) type serverfunctions, or the like. However, these are merely example of the typesof functions that are capable of being provided by visited CSN 1124 orhome CSN 1126, and the scope of the claimed subject matter is notlimited in these respects. Visited CSN 1124 may be referred to as avisited CSN in the case where visited CSN 1124 is not part of theregular service provider of fixed device 1116 or mobile device 1122, forexample where fixed 1116 or mobile device 1122 is roaming away fromtheir respective home CSN 1126, or where broadband wireless accesssystem 1100 is part of the regular service provider of fixed device 1116or mobile device 1122 but where broadband wireless access system 1100may be in another location or state that is not the main or homelocation of fixed device 1116 or mobile device 1122.

Fixed device 1116 may be located anywhere within range of one or bothbase stations 1114, 1120, such as in or near a home or business toprovide home or business customer broadband access to Internet 1110 viabase stations 1114, 1120 and ASN 1112, 1118, respectively, and home CSN1126. It is worthy to note that although fixed device 1116 is generallydisposed in a stationary location, it may be moved to differentlocations as needed. Mobile device 1122 may be utilized at one or morelocations if mobile device 1122 is within range of one or both basestations 1114, 1120, for example.

In accordance with one or more embodiments, operation support system(OSS) 1128 may be part of broadband wireless access system 1100 toprovide management functions for broadband wireless access system 1100and to provide interfaces between functional entities of broadbandwireless access system 1100. Broadband wireless access system 1100 ofFIG. 11 is merely one type of wireless network showing a certain numberof the components of broadband wireless access system 1100, and thescope of the claimed subject matter is not limited in these respects.

Some examples may be described using the expression “in one example” or“an example” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one example. The appearances ofthe phrase “in one example” in various places in the specification arenot necessarily all referring to the same example.

Some examples may be described using the expression “coupled”,“connected”, or “capable of being coupled” along with their derivatives.These terms are not necessarily intended as synonyms for each other. Forexample, descriptions using the terms “connected” and/or “coupled” mayindicate that two or more elements are in direct physical or electricalcontact with each other. The term “coupled,” however, may also mean thattwo or more elements are not in direct contact with each other, but yetstill co-operate or interact with each other.

The follow examples pertain to additional examples of technologiesdisclosed herein.

Example 1. An example apparatus may include logic, at least a portion ofthe logic in hardware, the logic to may receive first PM data for a VNF.The logic may also receive second PM data for NFVI arranged to supportthe VNF. The logic may also determine whether to initiate an NS LCMoperation with an NFVO or VNF LCM operation with a VNFM based onimplementation of a PM data correlation and detection of thresholdcrossing function using the first and/or the second PM data.

Example 2. The apparatus of example 1, the logic may be arranged as anEM for a 3GPP wireless network, the EM to receive the first PM datadirectly from the VNF. The logic may also receive the second PM datafrom VNFM coupled with a VIM that received the second PM data directlyfrom the NFVI. The logic may also determine to initiate the VNF LCMoperation with the VNFM based on implementation of the PM datacorrelation and detection of threshold crossing function using the firstand/or the second PM data.

Example 3. The apparatus of example 2, the VNF LCM operation may includeone or more of instantiate VNF instance, terminate VNF instance, queryVNF instance, scale VNF instance or update VNF instance.

Example 4. The apparatus of example 2, the EM may forward the first PMdata to an NM for the 3GPP wireless network. For these examples, the NMmay initiate the NS LCM operation with the NFVO based on implementationof the PM data correlation and detection of threshold crossing functionusing the first and/or the second PM data.

Example 5. The apparatus of example 2, the first PM data may be relatedto VNF application layer performance to include calls-per-second,number-of-subscribers, mean number of dedicated EPS bearers in activemode or peak number of dedicated EPS bearers in active mode.

Example 6. The apparatus of example 2, the second PM data may be relatedto one or more virtualized resources composed from the NFVI and consumedwhile supporting the VNF, the second PM data including vCPU powerconsumption, VM memory usage oversubscription, VM disk latency, meanvCPU usage or peak vCPU usage.

Example 7. The apparatus of example 1, the second PM data may be relatedto one or more virtualized resources composed from the NFVI and isassociated with the VNF consuming the virtualized resources whilesupporting the VNF and also related to a network service provided by theVNF.

Example 8. The apparatus of example 7, the logic may be arranged as anNM for a 3GPP wireless network. For these examples, the NM may receivethe first and second PM data from an EM for the 3GPP wireless networkand determine to initiate the NS LCM operation with the NFVO based onimplementation of the PM data correlation and detection of thresholdcrossing function using the first and/or the second PM data

Example 9. The apparatus of example 8, the NS LCM operation may includeone or more of instantiate network service, terminate network service,query network service, scale network service, update network service,create VNFFG, delete VNFFG, query VNFFG, update VNFFG, create VL, deleteVL, update VL or query VL.

Example 10. The apparatus of example 1, the PM data correlation anddetection threshold crossing function using the first and/or the secondPM data may include use of a plurality of PMs from among the firstand/or the second PM data to detect whether a given threshold has beencrossed.

Example 11. The apparatus of example 1 may also include a digitaldisplay coupled to the logic to present a user interface view.

Example 12. An example method may include receiving first PM data for aVNF. The method may also include receiving second PM data for NFVIarranged to support the VNF. The method may also include determiningwhether to initiate an NS LCM operation with an NFVO or a VNF LCMoperation with a VNFM based on performing a PM data correlation anddetection of threshold crossing function using the first and/or thesecond PM data.

Example 13. The method of example 12 may be implemented by an EM for a3GPP wireless network. The method may also include receiving the firstPM data directly from the VNF. The method may also include receiving thesecond PM data from the VNFM coupled with a VIM that received the secondPM data directly from the NFVI. The method may also include determiningto initiate the VNF LCM operation with the VNFM based on performing thePM data correlation and detection of threshold crossing function usingthe first and/or the second PM data.

Example 14. The method of example 13, the VNF LCM operation may includeone or more of instantiate VNF instance, terminate VNF instance, queryVNF instance, scale VNF instance or update VNF instance.

Example 15. The method of example 13 may also include forwarding thefirst PM data to an NM for the 3GPP wireless network. For theseexamples, the NM may initiate the NS LCM operation with the NFVO basedon performing of the PM data correlation and detection of thresholdcrossing function using the first and/or the second PM data.

Example 16. The method of example 13, the first PM data may be relatedto VNF application layer performance to include calls-per-second,number-of-subscribers, mean number of dedicated EPS bearers in activemode or peak number of dedicated EPS bearers in active mode.

Example 17. The method of example 13, the second PM data may be relatedto one or more virtualized resources composed from the NFVI and consumedwhile supporting the VNF, the second PM data including vCPU powerconsumption, VM memory usage oversubscription, VM disk latency, meanvCPU usage or peak vCPU usage.

Example 18. The method of example 12, the second PM data may be relatedto one or more virtualized resources composed from the NFVI and isassociated with the VNF consuming the virtualized resources whilesupporting the VNF and also related to a network service provided by theVNF.

Example 19. The method of example 12 may be implemented by an NM for a3GPP wireless network. The method may also include receiving the firstand second PM data from an EM for the 3GPP wireless network. The methodmay also include determining to initiate the NS LCM operation with theNFVO based on performing the PM data correlation and detection ofthreshold crossing function using the first and/or the second PM data.

Example 20. The method of example 19, the NS LCM operation may includeone or more of instantiate network service, terminate network service,query network service, scale network service, update network service,create VNFFG, delete VNFFG, query VNFFG, update VNFFG, create VL, deleteVL, update VL or query VL.

Example 21. The method of example 12, the PM data correlation anddetection threshold crossing function using the first and/or the secondPM data may include using a plurality of PMs from among the first and/orthe second PM data to detect whether a given threshold has been crossed.

Example 22. An example at least one machine readable medium may includea plurality of instructions that in response to being executed by systemmay cause the system to carry out a method according to any one ofexamples 12 to 21.

Example 23. An example apparatus may include means for performing themethods of any one of examples 12 to 21.

Example 24. An example at least one non-transitory machine readablemedium may include a plurality of instructions that in response to beingexecuted on a system for a 3GPP wireless network may cause the system toreceive first PM data for a VNF. The instructions may also cause thesystem to receive second PM data for NFVI arranged to support the VNFand determine whether to request an NS LCM operation with an NFVO or aVNF LCM operation with a VNFM based on performance of a PM datacorrelation and detection of threshold crossing function using the firstand/or the second PM data.

Example 25. The at least one non-transitory machine readable medium ofexample 24, the system comprising an EM for a 3GPP wireless network, theinstructions may further cause the EM to receive the first PM datadirectly from the VNF. The instructions may also cause the EM to receivethe second PM data from a VNFM coupled with a VIM that received thesecond PM data directly from the NFVI. The instructions may also causethe EM to determine to initiate the VNF LCM operation with the VNFMbased on implementation of the PM data correlation and detection ofthreshold crossing function using the first and/or the second PM data.

Example 26. The at least one non-transitory machine readable medium ofexample 25, the VNF LCM operation may include one or more of instantiateVNF instance, terminate VNF instance, query VNF instance, scale VNFinstance or update VNF instance.

Example 27. The at least one non-transitory machine readable medium ofexample 25, the instructions to further cause the EM to forward thefirst PM data to an NM for the 3GPP wireless network. For theseexamples, the NM may initiate the NS LCM operation with the NFVO basedon performance of the PM data correlation and detection of thresholdcrossing function using the first and/or the second PM data.

Example 28. The at least one non-transitory machine readable medium ofexample 25, the first PM data related to VNF application layerperformance may include calls-per-second, number-of-subscribers, meannumber of dedicated EPS bearers in active mode or peak number ofdedicated EPS bearers in active mode.

Example 29. The at least one non-transitory machine readable medium ofexample 25, the second PM data may be related to one or more virtualizedresources composed from the NFVI and consumed while supporting the VNF.Also, the second PM data may include vCPU power consumption, VM memoryusage oversubscription, VM disk latency, mean vCPU usage or peak vCPUusage.

Example 30. The at least one non-transitory machine readable medium ofexample 24, the second PM data may be related to one or more virtualizedresources composed from the NFVI and may be associated with the VNFconsuming the virtualized resources while supporting the VNF and mayalso be related to a network service provided by the VNF.

Example 31. The at least one non-transitory machine readable medium ofexample 24, the system may include an NM for a 3GPP wireless network,the instructions to further cause the NM to receive the first and secondPM data from an EM for the 3GPP wireless network. The instructions mayalso cause the NM to determine to initiate the NS LCM operation with theNFVO based on performance of the PM data correlation and detection ofthreshold crossing function using the first and/or the second PM data.

Example 32. The at least one non-transitory machine readable medium ofexample 31, the NS LCM operation may include one or more of instantiatenetwork service, terminate network service, query network service, scalenetwork service, update network service, create VNFFG, delete VNFFG,query VNFFG, update VNFFG, create VL, delete VL, update VL or query VL.

Example 33. The at least one non-transitory machine readable medium ofexample 24, the PM data correlation and detection threshold crossingfunction using the first and/or the second PM data may include use of aplurality of PMs from among the first and/or the second PM data todetect whether a given threshold has been crossed.

Example 34. An example apparatus may include logic, at least a portionof the logic in hardware, the logic may be arranged to operate as a VIMfor NFVI. The VIM may receive PM data generated by the NFVI while theNFVI supports one or more virtualized network functions (VNFs). The VIMmay also forward the PM data to an NFVO if the PM data is related to anetwork service provided by the one or more VNFs. The VIM may alsoforward the PM data to a VNFM arranged to manage the one or more VNFs ifthe PM data is related to one or more virtualized resources composedfrom the NFVI and consumed while the virtualized resources support theone or more VNFs.

Example 35. The apparatus of example 34, the PM data related to thenetwork service provided by the one or more VNFs may be forwarded fromthe NFVO to an NM for a 3GPP wireless network. For this example, the NMmay implement a PM data correlation and detection of threshold crossingfunction using the PM data related to the network service to determinewhether to initiate an NS LCM operation with the NFVO.

Example 36. The apparatus of example 35, the NS LCM operation mayinclude one or more of instantiate network service, terminate networkservice, query network service, scale network service, update networkservice, create VNFFG, delete VNFFG, query VNFFG, update VNFFG, createVL, delete VL, update VL or query VL.

Example 37. The apparatus of example 34, the PM data related to thenetwork service provided by the one or more VNFs may be forwarded fromthe VNFM to an EM for a 3GPP wireless network. For this example, the EMmay implement a PM data correlation and detection of threshold crossingfunction using the PM data related to the one or more virtualizedresources to determine whether to initiate a VNF LCM operation with theVNFM.

Example 38. The apparatus of example 37, the VNF LCM operation mayinclude one or more of instantiate VNF instance, terminate VNF instance,query VNF instance, scale VNF instance or update VNF instance.

Example 39. The apparatus of example 34, the PM data related to thenetwork service may include latency of one or more virtual linkssupporting the one or more VNFs, usage of the one or more virtual linkssupporting the one or more VNFs, average bandwidth used by the one ormore VNFs to provide the network service over a time interval, peakbandwidth used by the one or more VNFs to provide the network serviceover the time interval, number of VMs utilized by the one or more VNFsto provide the network service or number of vCPUs utilized by the one ormore VNFs to provide the network service.

Example 40. The apparatus of example 34, the PM data related to the oneor more virtualized resources may include vCPU power consumption, VMmemory usage oversubscription, VM disk latency, mean vCPU usage or peakvCPU usage.

Example 41. The apparatus of example 34 may also include a digitaldisplay to present a user interface view.

Example 42. An example method may include receiving, at a VIM formanaging NFVI, PM data generated by the NFVI while the NFVI supports oneor more VNFs. The method may also include forwarding the PM data to anNFVO if the PM data is related to a network service provided by the oneor more VNFs. The method may also include forwarding the PM data to aVNFM arranged to manage the one or more VNFs if the PM data is relatedto one or more virtualized resources composed from the NFVI and consumedwhile the virtualized resources support the one or more VNFs.

Example 43. The method of example 42, the PM data related to the networkservice provided by the one or more VNFs may be forwarded from the NFVOto an NM for a 3GPP wireless network. For this example, the NM mayimplement a PM data correlation and detection of threshold crossingfunction using the PM data related to the network service to determinewhether to initiate an NS LCM operation with the NFVO.

Example 44. The method of example 43, the NS LCM operation may includeone or more of instantiate network service, terminate network service,query network service, scale network service, update network service,create VNFFG, delete VNFFG, query VNFFG, update VNFFG, create VL, deleteVL, update VL or query VL.

Example 45. The method of example 42, the PM data related to the networkservice provided by the one or more VNFs may be forwarded from the VNFMto an EM for a 3GPP wireless network, the EM to implement a PM datacorrelation and detection of threshold crossing function using the PMdata related to the one or more virtualized resources to determinewhether to initiate a VNF LCM operation with the VNFM.

Example 46. The method of example 45, the VNF LCM operation may includeone or more of instantiate VNF instance, terminate VNF instance, queryVNF instance, scale VNF instance or update VNF instance.

Example 47. The method of example 42, the PM data related to the networkservice may include latency of one or more virtual links supporting theone or more VNFs, usage of the one or more virtual links supporting theone or more VNFs, average bandwidth used by the one or more VNFs toprovide the network service over a time interval, peak bandwidth used bythe one or more VNFs to provide the network service over the timeinterval, number of VMs utilized by the one or more VNFs to provide thenetwork service or number of vCPUs utilized by the one or more VNFs toprovide the network service.

Example 48. The method of example 42, the PM data related to the one ormore virtualized resources may include vCPU power consumption, VM memoryusage oversubscription, VM disk latency, mean vCPU usage or peak vCPUusage.

Example 49. An example at least one non-transitory machine readablemedium may include a plurality of instructions that in response to beingexecuted on a system cause the system to carry out a method according toany one of examples 42 to 48.

Example 50. An example apparatus may include means for performing themethods of any one of examples 42 to 48.

Example 51. At least one non-transitory machine readable medium mayinclude a plurality of instructions that in response to being executedon a system arranged to operate as a VIM for NFVI, causes the system toreceive PM data generated by the NFVI while the NFVI supports one ormore VNFs. The instructions may also cause the system to forward the PMdata to an NFVO if the PM data is related to a network service providedby the one or more VNFs. The instructions may also cause the system toforward the PM data to a VNFM arranged to manage the one or more VNFs ifthe PM data is related to one or more virtualized resources composedfrom the NFVI and consumed while the virtualized resources support theone or more VNFs.

Example 52. The at least one non-transitory machine readable medium ofexample 51, the PM data related to the network service provided by theone or more VNFs may be forwarded from the NFVO to an NM for a 3GPPwireless network. For this example, the NM may implement a PM datacorrelation and detection of threshold crossing function using the PMdata related to the network service to determine whether to initiate anNS LCM operation with the NFVO.

Example 53. The at least one non-transitory machine readable medium ofexample 52, the NS LCM operation may include one or more of instantiatenetwork service, terminate network service, query network service, scalenetwork service, update network service, create VNFFG, delete VNFFG,query VNFFG, update VNFFG, create VL, delete VL, update VL or query VL.

Example 54. The at least one non-transitory machine readable medium ofexample 51, the PM data related to the network service provided by theone or more VNFs may be forwarded from the VNFM to an EM for a 3GPPwireless network. For this example, the EM may implement a PM datacorrelation and detection of threshold crossing function using the PMdata related to the one or more virtualized resources to determinewhether to initiate a VNF LCM operation with the VNFM.

Example 55. The at least one non-transitory machine readable medium ofexample 54, the VNF LCM operation may include one or more of instantiateVNF instance, terminate VNF instance, query VNF instance, scale VNFinstance or update VNF instance.

Example 56. The at least one non-transitory machine readable medium ofexample 51, the PM data related to the network service may includelatency of one or more virtual links supporting the one or more VNFs,usage of the one or more virtual links supporting the one or more VNFs,average bandwidth used by the one or more VNFs to provide the networkservice over a time interval, peak bandwidth used by the one or moreVNFs to provide the network service over the time interval, number ofVMs utilized by the one or more VNFs to provide the network service ornumber of vCPUs utilized by the one or more VNFs to provide the networkservice.

Example 57. The at least one non-transitory machine readable medium ofexample 51, the PM data related to the one or more virtualized resourcesmay include vCPU power consumption, VM memory usage oversubscription, VMdisk latency, mean vCPU usage or peak vCPU usage.

It is emphasized that the Abstract of the Disclosure is provided tocomply with 37 C.F.R. Section 1.72(b), requiring an abstract that willallow the reader to quickly ascertain the nature of the technicaldisclosure. It is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the examples. Inaddition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single example for thepurpose of streamlining the disclosure.

This method of disclosure is not to be interpreted as reflecting anintention that the claimed examples require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed example. Thus the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separate example. In the appended claims, the terms“including” and “in which” are used as the plain-English equivalents ofthe respective terms “may include” and “wherein,” respectively.Moreover, the terms “first,” “second,” “third,” and so forth, are usedmerely as labels, and are not intended to impose numerical requirementson their objects.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. A method implemented by a network manager (NM)for a Third Generation Partnership Project (3GPP) wireless network, themethod comprising: receiving first performance measurement (PM) datarelated to a virtualized network function (VNF) from an element manager(EM) of the 3GPP wireless network, wherein the first PM data is used bya threshold crossing function performed at the NM; and determiningwhether to initiate a network services (NS) lifecycle management (LCM)operation with a network functions virtualization orchestrator (NFVO)based on one or more of: a detection of a threshold crossing by thethreshold crossing function using the first PM data; and the first PMdata.
 2. The method of claim 1, further comprising: receiving, from theEM, second PM data related to network functions virtualizationinfrastructure (NFVI) arranged to support the VNF.
 3. The method ofclaim 2, wherein determining whether to initiate the NS LCM operationwith the NFVO is further based on performing a PM data correlation usingthe first PM data and/or the second PM data.
 4. The method of claim 2,wherein the first PM data includes calls-per-second,number-of-subscribers, mean number of dedicated evolved packet system(EPS) bearers in active mode or peak number of dedicated EPS bearers inactive mode.
 5. The method of claim 2, wherein the second PM dataincludes virtual central processing unit (vCPU) power consumption,virtual machine (VM) memory usage oversubscription, VM disk latency,mean vCPU usage or peak vCPU usage.
 6. The method of claim 1, whereinthe NS LCM operation comprises an operation to scale network service. 7.The method of claim 1, wherein the threshold crossing function uses aplurality of PMs from among the first PM data to detect whether a giventhreshold has been crossed.
 8. A network manager (NM) for a ThirdGeneration Partnership Project (3GPP) wireless network, the NMcomprising: a processor to: receive first performance measurement (PM)data related to a virtualized network function (VNF) from an elementmanager (EM) of the 3GPP wireless network, wherein the first PM data isused by a threshold crossing function performed at the NM; and determinewhether to initiate a network services (NS) lifecycle management (LCM)operation with a network functions virtualization orchestrator (NFVO)based on one or more of: a detection of a threshold crossing by thethreshold crossing function using the first PM data, and the first PMdata.
 9. The NM of claim 8, wherein the processor is further to:receive, from the EM, second PM data related to network functionsvirtualization infrastructure (NFVI) arranged to support the VNF. 10.The NM of claim 9, wherein determining whether to initiate the NS LCMoperation with the NFVO is further based on a PM data correlation usingthe first PM data and the second PM data.
 11. The NM of claim 10,wherein the first PM data includes calls-per-second,number-of-subscribers, mean number of dedicated evolved packet system(EPS) bearers in active mode or peak number of dedicated EPS bearers inactive mode.
 12. The NM of claim 11, wherein the second PM data includesvirtual central processing unit (vCPU) power consumption, virtualmachine (VM) memory usage oversubscription, VM disk latency, mean vCPUusage or peak vCPU usage.
 13. The NM of claim 8, wherein the NS LCMoperation comprises an operation to scale network service.
 14. The NM ofclaim 8, wherein the threshold crossing function uses a plurality of PMsfrom among the first PM data to detect whether a given threshold hasbeen crossed.
 15. One or more processors to execute logic, the logiccomprising: a virtualized network function (VNF) performance measurement(PM) data module to receive VNF PM data related to a VNF from an elementmanager (EM) of a 3GPP wireless network, wherein the VNF PM data is usedby a threshold crossing function performed at a network manager (NM) ofthe 3GPP wireless network; and a function module to determine whether toinitiate a network services (NS) lifecycle management (LCM) operationwith a network functions virtualization orchestrator (NFVO) based on oneor more of: a detection of a threshold crossing by the thresholdcrossing function using the VNF PM data; and the VNF PM data.
 16. Theone or more processors of claim 15, wherein the VNF PM data includescalls-per-second, number-of-subscribers, mean number of dedicatedevolved packet system (EPS) bearers in active mode or peak number ofdedicated EPS bearers in active mode.
 17. The one or more processors ofclaim 16, wherein the logic further comprises: a network functionsvirtualization infrastructure (NFVI) PM data module to receive, from theEM, NFVI PM data related to a NFVI arranged to support the VNF.
 18. Theone or more processors of claim 17, wherein the NFVI PM data includesvirtual central processing unit (vCPU) power consumption, virtualmachine (VM) memory usage oversubscription, VM disk latency, mean vCPUusage or peak vCPU usage.
 19. The one or more processors of claim 18,wherein determining whether to initiate the NS LCM operation with theNFVO is further based on a PM data correlation using the VNF PM data andthe NFVI PM data.
 20. The one or more processors of claim 15, whereinthe NS LCM operation comprises an operation to scale network service.